home *** CD-ROM | disk | FTP | other *** search
Text File | 1996-04-24 | 2.2 KB | 66 lines | [TEXT/CWIE] |
- Release Notes
- InputSprocket 1.0 DR1
- 3/28/96
-
-
- 1. User Issues
- 2. Application Issues
- 3. Driver Issues
-
- 1. User Issues
-
- The InputSprocket currently does not support more than one application
- using it at a time and may crash if you launch more than one. You have
- been warned. As far as the applications that shipped with the DR1 release
- this would mean you can't launch Drone Zone and InputSprocketTest at the
- same time
-
- The InputSprocket test after it displays various lists will sit in a loop
- displaying InputSprocket events. You must press command period to end this
- loop. After you do so you may quit as you would from any other SIOUX
- app.
-
- The firebird driver will turn of keyboard actions that the driver would
- normally generate and then it does not restore that state. The thrustmaster
- driver doesn't ever turn them off so you will have to do that yourself to
- get good behavior.
-
- 2. Application Issues
-
- The user interface componenet is not present in this release.
-
- Error checking is only minimumally performed and sometimes parameters
- which specify buffer length may be ignored.
-
- Access to polled data may not be atomic in this release. However
- access to event based data should be correctly atomic.
-
- There is going to be a name revision of most or all of the functions.
-
- There currently unimplemented user interface component may undergo
- some revisions.
-
- There will be some minor changes including adding a list count and
- list of ElementReferences to the constructor for an element list.
- The string identifier may be moved to a different function to prepare
- for Copland.
-
- There will be some additions relating to keyboard and mouse emulation
- as well as a method to turn the keyboard and mouse drivers on and off.
-
- 3. Driver Issues
-
- The user interface component is not present in this release.
-
- For this release data of size other than 4 is not supported.
-
- There is going to be a name revision of most or all of the functions.
-
- There currently unimplemented user interface component may undergo
- some revisions.
-
- There will be some minor changes including ways to communicate
- if the driver should be supplying keyboard and mouse emulation.
- As well as having a way to tell the API to do keyboard and mouse
- emulation for the driver.
-